-
Notifications
You must be signed in to change notification settings - Fork 189
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Incorporate experimental and alpha features #4213
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This seems fine to me. I can see it under Next but not 8.5, which I think is the goal.
@christinaausley structure looks good - Have added some design suggestions around this here as well as naming ideas too. |
We won't use "experimental" in the official, shipped version. See my update on Slack - https://camunda.slack.com/archives/C0484UFR2VA/p1725571619654449 |
@camundom @melanie-butcher sounds like you are perhaps putting together some design ideas? Do we have any strong opinions around some of the potential naming terms based on the Slack thread linked above? Also happy to hop on a call and discuss. |
Hi @christinaausley, here's a link to the draft design for the docs, includes a revised structure for early access/experimental features, along with few open questions. Please let me know what you think. |
Thanks for meeting with me today @camundom -- please let me know if I can assist with incorporating the changes here once the finalities of the design are discussed with @bastiankoerber. |
Removing |
Hi @camundom -- based on your draft design, can I go ahead and update this PR so we have a place to put content before CCon? |
@akeller It's looking like I can start pulling some experimental CCon documentation into GitHub. How do we feel about merging those into this branch once the structure is ready to go? |
Doesn't matter to me! I'll leave it with the team to decide on names, etc. Also if it's easier to close this PR out and start fresh, that works too. |
Hi @christinaausley , yes that can be done. I've also received final approval to the design/structure that would be used for CCon. Please let me know if there's any way that I can help you with this. Thanks |
Thanks @camundom -- prepping this today and tomorrow. |
* initial poc commit * wip: sap odata connector * wip: further docs * docs: spell check * feat: first draft of the sap docs * initial edits * revise rfc connector * remove from sidebar for now * Update docs/guides/sap/btp-integration.md Co-authored-by: Cole Isaac <[email protected]> * Update docs/guides/sap/camunda-sap-integration.md Co-authored-by: Cole Isaac <[email protected]> * Update docs/guides/sap/rfc-connector.md Co-authored-by: Cole Isaac <[email protected]> * resolve comments * second review of sap content * fix link * resolve comments * move into components for now * Update docs/components/sap/odata-connector.md Co-authored-by: Mark Sellings <[email protected]> * Update docs/components/sap/odata-connector.md Co-authored-by: Mark Sellings <[email protected]> * Update docs/components/sap/odata-connector.md Co-authored-by: Mark Sellings <[email protected]> * Update docs/components/sap/rfc-connector.md Co-authored-by: Mark Sellings <[email protected]> * Update docs/components/sap/rfc-connector.md Co-authored-by: Mark Sellings <[email protected]> * Update docs/components/sap/rfc-connector.md Co-authored-by: Mark Sellings <[email protected]> --------- Co-authored-by: Volker Buzek <[email protected]> Co-authored-by: Volker Buzek <[email protected]> Co-authored-by: Volker Buzek <[email protected]> Co-authored-by: Christina Ausley <[email protected]> Co-authored-by: christinaausley <[email protected]> Co-authored-by: Cole Isaac <[email protected]> Co-authored-by: Mark Sellings <[email protected]>
This is ready for final review -- I will plan to release this tomorrow afternoon. CC @bastiankoerber |
👋 🤖 🤔 Hello! Did you make your changes in all the right places? These files were changed only in docs/. You might want to duplicate these changes in versioned_docs/version-8.6/.
You may have done this intentionally, but we wanted to point it out in case you didn't. You can read more about the versioning within our docs in our documentation guidelines. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I've reviewed the overview page but have already reviewed the other pages - just one possibly blocking issue with the table rows, but I'm aware you want to emrge this today so approving as this can be done ina. follow-up PR 👍
|
||
## Alpha features | ||
|
||
Alpha features are more developed and closer to becoming part of the product but may not yet be fully optimized or supported. Selected Camunda features and components are released as alpha versions to provide early access. By testing these features, you have the opportunity to participate in their development by sharing feedback before they reach General Availability (GA). |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Do we want to link to the Alpha features page? https://docs.camunda.io/docs/next/reference/alpha-features/
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Honestly we could probably move this entire page over as an "overview" to the alpha features section, but I consider that out of scope for this PR. Will open an additional issue to revisit.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I was going to provide similar feedback - we include definitions or explanations for alphas and minors on the release policy page as well. These should be linked so they reference each other. I'm ok with this being handled in a separate PR.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Cool. I'll launch another PR. Can I get a final approval from one of you so I can go ahead and release this?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Lgtm - great work! 🥇 👍
🧹 Preview environment for this PR has been torn down. |
Description
This PR creates an "Experimental" and "alpha" section in the Components area of the docs with a landing page, SAP, and RPA documentation.
When should this change go live?
hold
label or convert to draft PR) To release Oct 15 for CConPR Checklist
/versioned_docs
directory./docs
directory (aka/next/
).